home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
archiver
/
zlab_19c.zip
/
WHATS.NEW
< prev
next >
Wrap
Text File
|
1992-02-02
|
32KB
|
602 lines
##############################################################################
VERSION HISTORY (NEWEST TO OLDEST)
##############################################################################
ZipLab PLUS Version 1.9c
* Changes are NOT required(but may be desirable), in your configuration for
this version! Please see the "Rusty and Eddy" Protection below, and
run SETUP.EXE to add the appropriate entry if desired.
* Non-standard comm ports are back! I have talked with Jeff Sumburg, the
author of QBSerial (The communications routines used in ZipLab) about
the problems I was having with non-standard comm ports in an earlier
version of ZipLab, and he gave me some tips on using his code to enable
communications with ports which are not at the standard DOS supported
address and IRQ locations. Mostly his advice was "Jeeze Jeff, did you
read the manual?" <grin>. In any case, ZipLab PLUS will now get both the
IRQ and PORT ADDRESS from PCBoard.Dat. If you have set a non-standard comm
port with PCBSETUP, ZipLab PLUS will use them.
* "Rusy and Eddy" Protection(tm) - There are some BBS systems which insist
on putting annoying, space wasting BBS advertising in everything which
passes through their hands. There are even some who are so intent that you
read all about how many megabytes and Dual Standards they have that they
have a routine to create a new name for the BBS ad before they insert it.
A new feature of ZipLab PLUS will allow you to use the CRC32 value of the
ads you wish to remove, instead of just the name. All you do is use the
enclosed GETCRC.EXE program, to find the CRC32 value of the BBS
advertisement you wish to remove. Add this in the following format to a
file called "CRC.ADS" (NOTE! It MUST have this name).
00000000,filename.ext
Where "00000000" is the CRC32 value, and "filename.ext" is the name of the
BBS advertisement you wish to remove. You can use GETCRC to do this
automaticaly, by typing:
GETCRC filename.exe >>CRC.ADS {ENTER}
Then place the full path and name of CRC.ADS on a line in PTEST.CFG, just
as if it were any other BBS advertisement name you were adding. Now
ZipLab PLUS will find that pesky BBS add and delete it, even if it has
been renamed.
Please see the example PTEST.CFG to be sure you add CRC.ADS in the right
place and in the right format. NOTE! This feature will NOT work with
.LZH files at this time, as LHA only stores CRC16 values. It will work
with both archive and self-extracting .ZIP and .ARJ files.
* The parameter 'CRC' in the config file is no longer valid. I have removed
the program's ability to get the file CRC of the archive file, which was
then displayed on the line with the newest and oldest file dates. I am
currently working with the author of ZDCS, to provide hooks from ZipLab
to this fine product. There is just no need to weigh down the ZipLab
code with a function which is implemented in another product. If you
are using CRC in your .CFG file, please replace with FILES or NONE.
* The two most common "description" files are FILE_ID.DIZ and DESC.SDI.
ZipLab will now ignore these files in the date verification routines,
so the act of using a tool to add a FILE_ID.DIZ to an archive will not
cause it to pass date checking.
* Some corrections were made to the way "self-extracting" archives were
handled, and this feature should be more reliable.
* ZipLab will now handle removing and/or replacing comments in .ARJ file
formats, and will properly handle imbedded .ARJ files. I am using and
testing with ARJ version 2.30, and this version is recommended.
* Tons more work on trapping any possible errors which may occur. I am
now 99% positive that ZipLab can't "hang" your system at an "abort,
retry, fail?" prompt. Please let me know if have this occurs at any
time! I still have a few Sysops who are having problems with ZipLab
under DesqView (although most run it just fine), and a few with problems
under Lantastic (again, most are running with no problem). I am working
at isolating what set of conditions are giving these few people trouble,
and hope to have it pinned down soon.
ZipLab PLUS Version 1.9b
* NO Changes to your configuration are required from version 1.9a. Changes
ARE required from 1.8c or earlier.
* Well, the swapping routines I added in the first 1.9 version have turned
out to be a whole lot more trouble than they are worth. Instead of
solving memory problems for some people, the additon of these routines
seem to have caused no end of other problems for a larger group of folks.
I have removed the swapping routines for now, until I can find a method
which is stable with QuickBasic (particuarly in a QEMM/DesQView setup).
This does mean that some people who are in extremely memory constrained
conditions will NOT BE ABLE TO RUN ZIPLAB PLUS. Again, ZipLab will need
about 160K of RAM to run, and the ZIP/ARJ/LHA programs used in testing
will required additional memory (PKUNZIP needs about 80K more). If you
can't give ZipLab this much memory when running PCBTEST.BAT, then it
just isn't going to work for you right now...
* Aside from that, this version is mostly a lot of changes to tighten up
error detection and reporting. The code has been re-written to a large
extent to allow for better error trapping. Any problems should now be
correctly reported in PTEST.ERR, with a better explanation of what went
wrong, what file was being accessed, and when in the process the error
occured. More importantly, there should be lots less errors to begin
with. The code will handle missing files, incorrect PTEST.CFG parms,
and low-memory conditions in a much cleaner fashion.
* The one big feature change in this version is that ZipLab will now test
"self-extracting" archives. If you put ".EXE" as one of the extensions
you wish to pass, all .EXE files will be examined for the signatures of
the 3 supported archive types, and if found to be self-extracting files,
will be fully tested. If not self-extracting (but in fact just .EXE
files), they will be SCAN'd for virus infection, and then passed.
* Sam Smith has changed the format of the $DOOR.NAM file (where the
descriptions are held while testing) in the latest versions of ProDoor.
This version of ZipLab PLUS will correctly handle both the new and the
old $DOOR.NAM formats. Please let me know if there are any further
problems with Ziplab and ProDoor.
ZipLab PLUS Version 1.9a
* NO Changes to your configuration are required from version 1.9. Changes
ARE required from 1.8c or earlier.
* This is a really quick one, sorry. I found a problem with the swapping
routines on machines with no XMS or EMS memory. ZipLab was incorrectly
creating the swap file at one point in the process, and the "custom
comment" was not being inserted. All other processes were working fine,
and in any case - it's fixed... Again, sorry for the quick release.
ZipLab PLUS Version 1.9
* Changes to your configuration ARE required for this release! Run SETUP!
* This version of Ziplab will now swap itself to XMS, EMS or DISK (whatever
it can find, in that order) on all SHELL functions. This will mean a
significant reduction in the amount of memory required for PTest.Exe.
Please let me know if any problems are seen running in unusual memory
conditions, such as under DesqView, OmniView, Windows, or network software.
* A new version of DELF.COM is included in this version (no longer in the
DELF11.ZIP archive) which has been modified to take advantage of the
new "swap" capabilities of ZipLab. You must add the location of this
new versi